Change Order Policies

The Change Order Policy automates the Change Order workflow. The following information is set up in the Change Order Policy:

The fields that can drive the Change Order Policy.
The user who will own and manage the change order throughout its life cycle.
The type of approvals that will be performed within the change order.
The approval groups that can be attached to the change order.

The Change Order Policy can be written for any combination of the fields in the Change Order entry window. Some common fields which may drive the Change Order Policy may include:

Change Order Category – may drive ownership and workflow
Org Unit – may drive ownership

Writing the Change Order Policy

To write a Change Order Policy, you must be familiar with writing a test condition in SQL using the un-translated field names of the Change Order template entries to drive the policy. These SQL statements are not checked; therefore, human intervention is required.

The following are lists of translated and untranslated fields for change order:

Translated Field	Untranslated Field
Category	COC_CATEGORY
Title	DOC_TITLE
Due Date	CHO_DUE_DATE
Effective Date	DOC_EFFECTIVE_DATE
Expiration Date	DOC_EXPIRATION_DATE
Org Unit	CHO_ORU_CODE
Product	CHO_PRD_CODE
Process	CHO_PRC_CODE
Priority	CHO_XPR_RANK
Plant Area	CHO_PLA_CODE
Comment	DOC_MEMO

User Rights

The following rights must be assigned to a user for that user to manage or view change order policies:

Rights	Description
CPL_MANAGE	Allows the administrator to add new change order policies , modify existing policies, or delete policies.
CPL_VIEW	Allows the user to access change order policies for viewing and selecting.

NOTE: See Rights Groups for more information on assigning rights groups to users.